Enriching Database Query Responses using Data from External Data Sources

ABSTRACT

The subject disclosure is directed towards enriching database query responses using data from external data sources. When processing a database query seeking enriched data from an external data source, a request is communicated to the external data source based on the database query. An enriched database query response is generated based on data provided by the external data source. The enriched database query response may be combined with data returned via an internal database query operation, and/or inserted into a local database table.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is related to U.S. patent application Ser. No. ______entitled “RECOMMENDING DATA ENRICHMENTS,” having Docket No. 332801.01,and U.S. patent application Ser. No. ______ entitled “DATA CUSTODIAN ANDCURATION SYSTEM,” having Docket No. 332802.01.

BACKGROUND

Software application operation depends on efficient computing resourceusage. Hence, supporting data storage and processing mechanisms areneeded for facilitating a positive user experience.

Such software applications include database applications that access anenterprise's internal database comprising structured data records (e.g.,table data). The database applications are built on a developmentplatform for a database management system. When a user communicates adatabase query, a database application accesses the internal databaseand (ordinarily) provides a response comprising table data that matchesthe database query.

In addition to internal data, users sometimes want to access data froman external data source or sources, such as to view such data along withretrieved internal database data. In order to do so, an application(data source provider) needs to be developed that understands how tocommunicate with each external source, e.g., its authentication model,communication protocols (connection strings) and/or any otherinformation such as billing requirements. Developing such an applicationis beyond the ability and/or too time consuming for a typical queryauthor who generally just wants to analyze the data.

SUMMARY

This Summary is provided to introduce a selection of representativeconcepts in a simplified form that are further described below in theDetailed Description. This Summary is not intended to identify keyfeatures or essential features of the claimed subject matter, nor is itintended to be used in any way that would limit the scope of the claimedsubject matter.

Briefly, various aspects of the subject matter described herein aredirected towards maintaining a translation mechanism that allows dataretrieved from internal database queries to be enriched with data fromexternal data sources, using straightforward query commands. In oneaspect, the translation mechanism facilitates the retrieval of externaldata because separate providers are not needed for different externaldata sources. There is no need for a query author or applicationdeveloper to deal with how database queries are authenticated, how tabledata is imported from the external data sources or how a user is billedfor access, for example.

In another aspect, an enrichment server uses the translation mechanismto combine an internal database with table data from one or moreexternal databases. Because the internal database may include non-public(i.e., private) data, the enrichment server enables a seamlessaugmentation of the non-public data with various public information.

In one aspect, the enrichment server extracts parameters from thedatabase query from which an entity is identified. The entity includes agrouping of data types as components whose values are requested by auser. The parameters also include values that are used as searchcriteria or the like for selecting data from the external data sources.Using these parameters, the translation mechanism initiates appropriatenative function calls of a protocol for requesting data from theexternal data sources.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIG. 1 is a block diagram illustrating an exemplary system for enrichingdatabase query responses using data from external data sources.

FIG. 2 is a flow diagram illustrating steps for enriching database queryresponses using data from external data sources according to one exampleimplementation.

FIG. 3 is a flow diagram illustrating steps for using a directory tocommunicate requests for various information to an external data sourceaccording to one example implementation.

FIG. 4 is a flow diagram illustrating steps for converting data fromexternal data sources into an enriched database query response accordingto one example implementation.

FIG. 5 is a flow diagram illustrating steps for building a directory fortranslating a database query into native requests for an external datasource according to one example implementation.

FIG. 6 is a flow diagram illustrating steps for mapping entitycomponents to external data sources according to one exampleimplementation.

FIG. 7 is a block diagram representing exemplary non-limiting networkedenvironments in which various embodiments described herein can beimplemented.

FIG. 8 is a block diagram representing an exemplary non-limitingcomputing system or operating environment in which one or more aspectsof various embodiments described herein can be implemented.

DETAILED DESCRIPTION

Various aspects of the technology described herein are generallydirected towards enriching database query responses using data that isextracted from external data sources. A database query includes one ormore parameters specifying one or more criteria for selecting data fromthe external data sources. One exemplary parameter includes an entityidentifier (e.g., a name) of a group of data types. Each data type mayinclude one or more other data types. Other exemplary parameters includeone or more values for one or more data types of the group of datatypes. Some other exemplary parameters may be contextual parameters thatlimit the values returned by the external data source to a particulartime and/or location, for example. Because enriched responses to thedatabase query include table data, the group of data types defines oneor more columns, while the one or more values define one or more rows.In one exemplary implementation, column data within each row of thetable data corresponds with the one or more values.

In one exemplary implementation, the database query pertains toenriching company data with various information exemplified as financialinformation, such as stock prices, employee statistics, earningsreports, market capitalization values (“market caps”), recent stockticker prices and/or the like. One or more external data sources, suchas financial news media, stock markets, search engines and/or the like,provide the various financial information for the one or more companynames in response to native function calls or queries (“requests”)requesting such data. Data types that define portions of the variousfinancial information constitute an entity. Hence, the database queryincludes an entity name and one or more company names as parameters.

An exemplary entity includes a number of components (i.e., data types),including components representing a number of employees, a market capand a stock price. Many other components may be included in the entity,e.g., company officers, gross sales, state of incorporation, years inexistence, and so forth. In order to access such data from an externalsource, a translation mechanism provides one or more exemplaryparameters, including any of the entity components (e.g., identified ina user query), and instructs connectivity software running at anappropriate external data source to execute a native function.Consequently, the connectivity software returns values for the number ofemployees, the market cap and/or the stock price, for example, if thoseare specified.

By way of example, consider an enterprise with a “companies” table namedC, containing rows of company names with a column of zipcode data (amonglikely many other columns) for various rows of companies. Consider thatthe internal database does not include stock ticker data or the numberof employees for each company, but that such information is availablefrom external sources. To view data formatted as name, zipcode, tickerand num_employees, heretofore a custom application (provider) was neededto merge the internal query results with the data from external sources.With data enrichment, a user need only specify pre-defined entity (e.g.,“CompanyFinancial”) that includes the appropriate components such asticker, num_employees, market_cap, and so forth, and submit anappropriate query:

SELECT name, zipcode, ticker, num_employees

FROM Companies c

ENRICH on CompanyFinancial (c.name)

The first line specifies the columns of data to retrieve, of which nameand zipcode are available from the enterprise's internal database, whileticker and num_employees are available from an external source (orsources). The second line indicates the table to enrich. The third lineis the data enrichment, which specifies the predefined entity“CompanyFinancial” that includes the components for the external data,with the c.name parameter specifying which companies to return externaldata for, namely those in the “Companies c” table. Note that the usercan view the “CompanyFinancial” entity to determine that the needed datacolumns (ticker and num_employees in this example) will be satisfied byspecifying this entity.

If one of the entity components, such as the number of employees, is notavailable (or remains unknown) from one data source, the translationmechanism may instruct connectivity software running at another externaldata source to execute a different native function in order to accessthe unknown entity component. Hence, the translation mechanism replacesthe need for one or more data separate providers to communicate witheach type of external data source.

Because an external data source may utilize a unique or proprietaryprotocol (e.g., Application Programming Interface (API)) to communicatedata, a translation mechanism accesses configuration data (e.g.,maintained in a directory) to configure a function call or remote querythat is compatible with such a protocol. The function call or remotequery includes criteria for identifying some of the various information(e.g., financial information) to use for enrichment. After thetranslation mechanism initiates the function call or query, the externaldata source returns data matching such criteria. Because the data isarranged in accordance with a native format, the translation mechanismconverts the data into compatible table data.

For example, the translation mechanism may call a function requesting aparticular company stock price from a stock market database. Such a callincludes a specific company name (or symbol) along with some indication(e.g., an attribute) indicating that the stock price is requested. Thestock price is communicated to the translation mechanism in a nativeformat. The translation mechanism extracts the stock price and insertsthe stock price in the table data that forms a portion of an enricheddatabase query response. In turn, the table data may be used to populateone or more columns of an internal database of the enterprise's data,including private data.

As mentioned above, some of the exemplary parameters may includecontextual parameters that specify a location and/or time value. Thetranslation mechanism uses the contextual parameters to identify datathat corresponds with the location and/or the time value from theexternal data source. For example, the translation mechanism uses aspecific date/time as a native function call parameter to select a stockprice at the specific data/time. As another example, the translationmechanism initiates another native function call for computing anaverage stock price over a time interval (e.g., a number of days).

In an alternate exemplary implementation, the database query includesparameters for enriching private company data with various newsinformation at or near a particular geographic location, which may berepresented as a physical location (e.g., geographic or geodeticcoordinates) or an Internet resource location (e.g., an InternetProtocol (IP) address). For example, the translation mechanism mayinitiate a native function call for company-related news within a rangeof a certain Global Positioning System (GPS) location. The nativefunction call may further request company-related news for a particulartime period, such as historical news or current news.

FIG. 1 is a block diagram illustrating an exemplary system for enrichingdatabase query responses using data from external data sources. Theexemplary system (e.g., implemented in one server among many servers)may support various database services. The exemplary system includesvarious example components, such as a SQL engine 102, an enrichmentserver 104 and a translation mechanism 106 as described herein. Theenrichment server 104 may be one or more servers comprising anenrichment service.

The SQL engine 102 receives database queries including variousparameters (i.e., sometimes referred to as enrichment parameters), suchas an entity identifier. The enrichment server 104 may access entitydata 108 and verify that each component in the query is available frominternal data 109 or via an entity that matches the entity identifier.For external components of the entity, the enrichment server 104 usesthe translation mechanism 106 to access data at one or more externaldata sources 110 ₁-110 _(n) and select values for various entitycomponents. These values may be stored in a form of table data within anenriched database query response that is communicated to the SQL engine102 via the enrichment server 104. In one implementation, the SQL engine102 is configured to populate portions (e.g., one or more columns oftable data) of an internal database 109 with the enriched database queryresponse.

In order to know how to communicate with each external source, thetranslation mechanism accesses a directory 112 with informationmaintained for each data source that corresponds to an entity component.For example, the directory 112 has entries for each external data source110 ₁-110 _(n), with each entry defining a protocol for communicatingdata with the external data source including native function calls, dataformats, billing procedures, security credentials and/or the like. Ascan be readily appreciated, instead of or in addition to a directory,any suitable mechanism may be used to determine such information,including maintaining the protocol/related data in another data store,hard coding the protocol/related data into the translation mechanism andso forth.

The enrichment server 104 and the translation mechanism 106 may bestored and operated at a local computer/network to control access tolocal and/or networked databases. Alternatively, the enrichment server104 and/or the translation mechanism 106 may be included in cloudcomputing applications where the local computer primarily functions asan interface for a share of computing resources at a remote server datacenter. While the cloud computing applications store the table data inan internal database, the internal database is not stored at the localcomputer, for example.

According to one example implementation, the enrichment server 104 mayutilize a policy 114 to map each of the various entity components to anappropriate external data source amongst the plurality of data sources110 ₁-110 _(n). For example, the policy 114 may include preferencesassociated with selecting the appropriate external data source. As amore particular example, the policy 114 may indicate a preference forfree data services over commercial/paid data services, whereby theenrichment server 104 selects a commercial/paid data service only if afree option does not exist; a price limit may be specified in the policyas well. As another example, the policy 114 may assign a high priorityto a specific data source. Unless a value for an entity component cannotbe retrieved or computed, the enrichment server 104 uses that specificdata source to access data for enriching the database query response.

According to one exemplary implementation, the plurality of externaldata sources 110 ₁-110 _(n) include any type of remote or Internet dataservice (e.g., data feeds, reports, commercial or free databases, searchengines and/or the like) from which table data is retrieved and thenused to generate an enriched database query response. Each of theexternal data sources 110 ₁-110 _(n) implements a particular protocolthat allows other computer systems to access the table data. Theparticular protocol may include an Application Programming Interface inwhich calling certain functions retrieves portions of the table data.Because the certain functions are native to the particular, they may bereferred to as native functions.

Input parameters for the native functions identify the portions of thetable data to be returned. For example, the translation mechanism 106calls a function with input parameters specifying a company name and arequested data type, such as a current stock price. One of the externaldata sources searches a database that provides stock prices and returnstable data comprising the company name and the current stock price. Asanother example, the translation mechanism 106 may request a stock pricefor a previous day, such as yesterday. In addition to the company name,the input parameters include a parameter specifying a day.

FIG. 2 is a flow diagram illustrating steps for enriching database queryresponses using data from external data sources according to one exampleimplementation. Steps depicted in FIG. 2 commence at step 202 andproceed to step 204 when database queries are processed by the SQLengine 104. Step 204 represents recognition of enrichment parameterswithin a database query and transmission of the database query to theenrichment server 104.

Step 206 illustrates extraction of the enrichment parameters from thedatabase query, which includes an entity identifier and one or morevalues of one or more entity components. As described herein, theseentity components include data types associated with enriching thedatabase query. Results from external data sources correspond with theone or more values as also described herein. Step 208 represents themapping of the entity components to external data sources. One exemplaryimplementation of Step 208 is illustrated in FIG. 6 in which a policydetermines which external data source to use for retrieving data for aparticular entity component.

Step 210 implements the translation mechanism 106, which produces andcommunicates native requests for various data to the external datasources. The native requests are configured in accordance with aprotocol for connecting to the external data sources, executingcompatible commands and retrieving results. In one example, the nativerequests include native function calls that are implemented by theexternal data sources. FIG. 3 illustrates an exemplary implementation ofStep 210 in which a directory is used to translate the database queryinto such native function calls requesting data for the entitycomponents.

Step 212 is directed to processing data received from the external datasources as a response to the native requests. In one exemplaryimplementation, the translation mechanism 106 converts the data providedby the external data source into table data that is used to generate anenriched database query response. The enrichment server 204 communicatesthe enriched database query response to the SQL engine 102, whichreturns a view of the enriched table response and/or inserts the tabledata into an internal table of an internal database, e.g., according toa schema. The internal table may be refreshed automatically on ascheduled basis or the like, e.g., by automatically generating a newquery for external data and using the data in the enriched data responseto insert the updated data.

Optionally, the enrichment server 204 collects statistics regardingbilling activity, data source diagnostics and/or the like. Thesestatistics may be used for various purposes, such as auditing billingexpenses, analyzing data sources and updating the policy. For example,the policy may include a usage limit for a particular data source. Ifthe statistics indicate that the usage limit has been reached, anotherdata source may be selected from the policy. Step 214 representstermination of enriching database query responses.

FIG. 3 is a flow diagram illustrating steps for using a directory tocommunicate requests for various information to an external data sourceaccording to one example implementation. These requests are configuredto be a native command for the external data source. The enrichmentserver 104 uses the translation mechanism to produce these requestsbased on a database query that is transmitted from the SQL engine 102.Steps depicted in FIG. 3 commence at step 302 and proceed to step 304where the enrichment server 104 accesses a directory implementing thetranslation mechanism 106.

Step 306 represents an examination of a directory entry associated withthe external data source. Step 308 refers to identifying a protocol forcommunicating with the external data source. The directory entry definesa protocol for communicating data with the external data sourceincluding native function calls, data formats, billing procedures,security credentials and/or the like. Hence, such a protocol is used bythe translation mechanism 106 to initiate one or more native functioncalls to the external data source.

Step 310 is directed to connecting with the external data source. Theprotocol within the directory entry also includes a location, such as anIP address, as well as any authenticating procedures for the externaldata source. For example, an account user name and password may berequired for accessing the external data source. After establishing asession (e.g., an HTTP or HTTPS session), the translation mechanism 106selects one or more specific databases or tables and initiates callsrequesting various information as illustrated by step 312. These callsinclude native function calls associated with an API of the externaldata source. Step 314 refers to termination of using the directory tocommunicate requests for various information to the external datasource.

FIG. 4 is a flow diagram illustrating steps for converting data fromexternal data sources into an enriched database query response accordingto one example implementation. Steps depicted in FIG. 4 commence at step402 and proceed to step 404 when the translation mechanism 106 receivesdata from the external data sources in response to native requests forvarious information, such as financial or news information.

Step 406 is directed to examining a format associated with the datareceived from the external data sources (although the format may beknown in advance from information in the directory, for example). In oneexemplary implementation, a particular external data source returnsvalues in a unique format, such as JavaScript Object Notation (JSON)format. The translation mechanism 106 converts these values into tabledata and prepares an enriched database query response as represented instep 408. The translation mechanism 106 may perform additionalprocessing on these values, such as aggregating stock prices over aperiod of time and computing a mean or median stock price.

Step 410 is directed to returning a view of the enriched table and/orpopulating an internal database using the enriched database queryresponse. Via the enrichment server 104, the table data created from thevalues that were returned by the particular external data source may beinserted into a certain table or one or more columns within the internaldatabase according to one exemplary implementation. In one example, thetable data shares a similar schema with the certain table rendering theinsertion operation into a series of copy data operations.Alternatively, the certain table is blank or a temporary table outsideof a relational paradigm associated with the internal database. Step 412signifies a completion of the enriched database query response.

FIG. 5 is a flow diagram illustrating steps for building a directory fortranslating a database query into native requests for an external datasource according to one example implementation. The directory forms aportion of the translation mechanism 106. Steps depicted in FIG. 5commence at step 502 and proceed to step 504 when the translationmechanism 106 generates a blank directory entry.

As explained further below, the translation mechanism 106 stores variousinformation in the blank directory entry, such as a protocol forcommunicating with the external data source, according to one exemplaryimplementation. The protocol defines native functions calls forrequesting information and formats for organizing the requestedinformation. In one example, the protocol requires various credentialssuch as a username and password.

Step 506 is directed to connecting with the external data source. Forexample, the translation mechanism 106 creates a session using an IPaddress with an interface to the external data source, such as anApplication Programming Interface (API). The translation mechanism 106proceeds to communicate with the external data source via the interface,which is represented by step 508. In some implementations, thetranslation mechanism 106 uses the interface to enumerate each availabledatabase and selects an appropriate database in response to a policy asdescribed herein.

Step 510 refers to determining requirements for using a protocolassociated with the external data source. In one exemplaryimplementation, the translation mechanism 106 identifies functions thatare executable by the interface and configured to return variousinformation. These functions are native to the external data source andenable access to one or more available databases. The translationmechanism 106 also determines which credentials are needed to search theone or more available databases according one example. In an alternateexample, the translation mechanism also determines whether a unique orpropriety format is used to exchange data with the external database.Any information regarding the requirements for using the protocol isstored in the blank directory entry as represented by step 512. Whencomplete, the directory entry is used to update the directory, which isdenoted by step 514.

Step 516 represents a decision as to whether to further update thedirectory with another entry for a next external data source. If thereare more external data sources to examine, steps 504 to 514 arerepeated. If, on the other hand, there are no more external data sourcesto examine, step 516 is performed during which the building of thedirectory terminates. The directory may be rebuilt and/or updated at anyappropriate time, e.g., whenever a new data source is added or changesits protocol.

FIG. 6 is a flow diagram illustrating steps for mapping entitycomponents to external data sources according to one exampleimplementation. Each entity component includes a data type whose valueor values enrich a database query response. As mentioned in the presentdisclosure, a database query specifies an entity that represents agrouping of the data types. Steps depicted in FIG. 6 commence at step602 and proceed to step 604 when the translation mechanism 106 examinesan entity component.

Step 606 refers to identifying matching external data sources for theentity component. The matching external data sources are configured toprovide information that corresponds with the entity component. Forexample, the matching external data sources provide data having a samedata type as the entity component. The data provided by the matchingexternal data sources may require further processing. As an example,such data includes values of which an algorithm uses as input parametersin order to compute another value, which is stored in the entitycomponent.

After identifying the matching external data sources, step 608 isdirected to accessing a policy for selecting an appropriate one torequest various information, which is represented as step 610. In oneexemplary implementation, the policy includes preferences for particularexternal data sources based on various factors, such as billingrequirements, performance and/or the like. In one example, the policyindicates a preference for free data sources. As such, only free ones ofthe matching external data sources are considered options. If more thanone matching external data source is free, any of them can be selected.

Step 612 represents a decision as to mapping another entity component toan appropriate external data source. If there are more entitycomponents, the enrichment server, via the translation mechanism 106,returns to Step 604 are repeats each step until 610 for a next entitycomponent. If, on the other hand, there are no more entity components,the mapping of the entity components terminates, which is represented bystep 614.

FIG. 7 provides a schematic diagram of an exemplary networked ordistributed computing environment. The distributed computing environmentcomprises computing objects 710, 712, etc., and computing objects ordevices 720, 722, 724, 726, 728, etc., which may include programs,methods, data stores, programmable logic, etc. as represented by exampleapplications 730, 732, 734, 736, 738. It can be appreciated thatcomputing objects 710, 712, etc. and computing objects or devices 720,722, 724, 726, 728, etc. may comprise different devices, such aspersonal digital assistants (PDAs), audio/video devices, mobile phones,MP3 players, personal computers, laptops, etc.

Each computing object 710, 712, etc. and computing objects or devices720, 722, 724, 726, 728, etc. can communicate with one or more othercomputing objects 710, 712, etc. and computing objects or devices 720,722, 724, 726, 728, etc. by way of the communications network 740,either directly or indirectly. Even though illustrated as a singleelement in FIG. 7, communications network 740 may comprise othercomputing objects and computing devices that provide services to thesystem of FIG. 7, and/or may represent multiple interconnected networks,which are not shown. Each computing object 710, 712, etc. or computingobject or device 720, 722, 724, 726, 728, etc. can also contain anapplication, such as applications 730, 732, 734, 736, 738, that mightmake use of an API, or other object, software, firmware and/or hardware,suitable for communication with or implementation of the applicationprovided in accordance with various embodiments of the subjectdisclosure.

There are a variety of systems, components, and network configurationsthat support distributed computing environments. For example, computingsystems can be connected together by wired or wireless systems, by localnetworks or widely distributed networks. Currently, many networks arecoupled to the Internet, which provides an infrastructure for widelydistributed computing and encompasses many different networks, thoughany network infrastructure can be used for exemplary communications madeincident to the systems as described in various embodiments.

Thus, a host of network topologies and network infrastructures, such asclient/server, peer-to-peer, or hybrid architectures, can be utilized.The “client” is a member of a class or group that uses the services ofanother class or group to which it is not related. A client can be aprocess, e.g., roughly a set of instructions or tasks, that requests aservice provided by another program or process. The client processutilizes the requested service without having to “know” any workingdetails about the other program or the service itself.

In a client/server architecture, particularly a networked system, aclient is usually a computer that accesses shared network resourcesprovided by another computer, e.g., a server. In the illustration ofFIG. 7, as a non-limiting example, computing objects or devices 720,722, 724, 726, 728, etc. can be thought of as clients and computingobjects 710, 712, etc. can be thought of as servers where computingobjects 710, 712, etc., acting as servers provide data services, such asreceiving data from client computing objects or devices 720, 722, 724,726, 728, etc., storing of data, processing of data, transmitting datato client computing objects or devices 720, 722, 724, 726, 728, etc.,although any computer can be considered a client, a server, or both,depending on the circumstances.

A server is typically a remote computer system accessible over a remoteor local network, such as the Internet or wireless networkinfrastructures. The client process may be active in a first computersystem, and the server process may be active in a second computersystem, communicating with one another over a communications medium,thus providing distributed functionality and allowing multiple clientsto take advantage of the information-gathering capabilities of theserver.

In a network environment in which the communications network 740 or busis the Internet, for example, the computing objects 710, 712, etc. canbe Web servers with which other computing objects or devices 720, 722,724, 726, 728, etc. communicate via any of a number of known protocols,such as the hypertext transfer protocol (HTTP). Computing objects 710,712, etc. acting as servers may also serve as clients, e.g., computingobjects or devices 720, 722, 724, 726, 728, etc., as may becharacteristic of a distributed computing environment.

Exemplary Computing Device

As mentioned, advantageously, the techniques described herein can beapplied to any device. It can be understood, therefore, that handheld,portable and other computing devices and computing objects of all kindsare contemplated for use in connection with the various embodiments.Accordingly, the below general purpose remote computer described belowin FIG. 8 is but one example of a computing device.

Embodiments can partly be implemented via an operating system, for useby a developer of services for a device or object, and/or includedwithin application software that operates to perform one or morefunctional aspects of the various embodiments described herein. Softwaremay be described in the general context of computer executableinstructions, such as program modules, being executed by one or morecomputers, such as client workstations, servers or other devices. Thoseskilled in the art will appreciate that computer systems have a varietyof configurations and protocols that can be used to communicate data,and thus, no particular configuration or protocol is consideredlimiting.

FIG. 8 thus illustrates an example of a suitable computing systemenvironment 800 in which one or aspects of the embodiments describedherein can be implemented, although as made clear above, the computingsystem environment 800 is only one example of a suitable computingenvironment and is not intended to suggest any limitation as to scope ofuse or functionality. In addition, the computing system environment 800is not intended to be interpreted as having any dependency relating toany one or combination of components illustrated in the exemplarycomputing system environment 800.

With reference to FIG. 8, an exemplary remote device for implementingone or more embodiments includes a general purpose computing device inthe form of a computer 810. Components of computer 810 may include, butare not limited to, a processing unit 820, a system memory 830, and asystem bus 822 that couples various system components including thesystem memory to the processing unit 820.

Computer 810 typically includes a variety of computer readable media andcan be any available media that can be accessed by computer 810. Thesystem memory 830 may include computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) and/orrandom access memory (RAM). By way of example, and not limitation,system memory 830 may also include an operating system, applicationprograms, other program modules, and program data.

A user can enter commands and information into the computer 810 throughinput devices 840. A monitor or other type of display device is alsoconnected to the system bus 822 via an interface, such as outputinterface 850. In addition to a monitor, computers can also includeother peripheral output devices such as speakers and a printer, whichmay be connected through output interface 850.

The computer 810 may operate in a networked or distributed environmentusing logical connections to one or more other remote computers, such asremote computer 870. The remote computer 870 may be a personal computer,a server, a router, a network PC, a peer device or other common networknode, or any other remote media consumption or transmission device, andmay include any or all of the elements described above relative to thecomputer 810. The logical connections depicted in FIG. 8 include anetwork 872, such local area network (LAN) or a wide area network (WAN),but may also include other networks/buses. Such networking environmentsare commonplace in homes, offices, enterprise-wide computer networks,intranets and the Internet.

As mentioned above, while exemplary embodiments have been described inconnection with various computing devices and network architectures, theunderlying concepts may be applied to any network system and anycomputing device or system in which it is desirable to improveefficiency of resource usage.

Also, there are multiple ways to implement the same or similarfunctionality, e.g., an appropriate API, tool kit, driver code,operating system, control, standalone or downloadable software object,etc. which enables applications and services to take advantage of thetechniques provided herein. Thus, embodiments herein are contemplatedfrom the standpoint of an API (or other software object), as well asfrom a software or hardware object that implements one or moreembodiments as described herein. Thus, various embodiments describedherein can have aspects that are wholly in hardware, partly in hardwareand partly in software, as well as in software.

The word “exemplary” is used herein to mean serving as an example,instance, or illustration. For the avoidance of doubt, the subjectmatter disclosed herein is not limited by such examples. In addition,any aspect or design described herein as “exemplary” is not necessarilyto be construed as preferred or advantageous over other aspects ordesigns, nor is it meant to preclude equivalent exemplary structures andtechniques known to those of ordinary skill in the art. Furthermore, tothe extent that the terms “includes,” “has,” “contains,” and othersimilar words are used, for the avoidance of doubt, such terms areintended to be inclusive in a manner similar to the term “comprising” asan open transition word without precluding any additional or otherelements when employed in a claim.

As mentioned, the various techniques described herein may be implementedin connection with hardware or software or, where appropriate, with acombination of both. As used herein, the terms “component,” “module,”“system” and the like are likewise intended to refer to acomputer-related entity, either hardware, a combination of hardware andsoftware, software, or software in execution. For example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon computer and the computer can be a component. One or more componentsmay reside within a process and/or thread of execution and a componentmay be localized on one computer and/or distributed between two or morecomputers.

The aforementioned systems have been described with respect tointeraction between several components. It can be appreciated that suchsystems and components can include those components or specifiedsub-components, some of the specified components or sub-components,and/or additional components, and according to various permutations andcombinations of the foregoing. Sub-components can also be implemented ascomponents communicatively coupled to other components rather thanincluded within parent components (hierarchical). Additionally, it canbe noted that one or more components may be combined into a singlecomponent providing aggregate functionality or divided into severalseparate sub-components, and that any one or more middle layers, such asa management layer, may be provided to communicatively couple to suchsub-components in order to provide integrated functionality. Anycomponents described herein may also interact with one or more othercomponents not specifically described herein but generally known bythose of skill in the art.

In view of the exemplary systems described herein, methodologies thatmay be implemented in accordance with the described subject matter canalso be appreciated with reference to the flowcharts of the variousfigures. While for purposes of simplicity of explanation, themethodologies are shown and described as a series of blocks, it is to beunderstood and appreciated that the various embodiments are not limitedby the order of the blocks, as some blocks may occur in different ordersand/or concurrently with other blocks from what is depicted anddescribed herein. Where non-sequential, or branched, flow is illustratedvia flowchart, it can be appreciated that various other branches, flowpaths, and orders of the blocks, may be implemented which achieve thesame or a similar result. Moreover, some illustrated blocks are optionalin implementing the methodologies described hereinafter.

CONCLUSION

While the invention is susceptible to various modifications andalternative constructions, certain illustrated embodiments thereof areshown in the drawings and have been described above in detail. It shouldbe understood, however, that there is no intention to limit theinvention to the specific forms disclosed, but on the contrary, theintention is to cover all modifications, alternative constructions, andequivalents falling within the spirit and scope of the invention.

In addition to the various embodiments described herein, it is to beunderstood that other similar embodiments can be used or modificationsand additions can be made to the described embodiment(s) for performingthe same or equivalent function of the corresponding embodiment(s)without deviating therefrom. Still further, multiple processing chips ormultiple devices can share the performance of one or more functionsdescribed herein, and similarly, storage can be effected across aplurality of devices. Accordingly, the invention is not to be limited toany single embodiment, but rather is to be construed in breadth, spiritand scope in accordance with the appended claims.

1. In a computing environment, a method performed at least in part on atleast one processor, comprising: processing a database query, includingcommunicating one or more native requests to at least one external datasource based on the database query and generating an enriched databasequery response based on data provided by the at least one external datasource in response to the native requests.
 2. The method of claim 1,wherein processing the database query further comprises mapping at leastone entity component to the at least one external data source.
 3. Themethod of claim 2, wherein mapping the at least one entity componentfurther comprises selecting the at least one external data source from aplurality of external data sources using a policy.
 4. The method ofclaim 1, wherein communicating the native requests further comprisestranslating the database query into the one or more native requests,including processing an entity associated with the database query andfor each entity component, identifying a protocol for a correspondingexternal data source and producing a native request based on theprotocol.
 5. The method of claim 4, wherein translating the databasequery further includes accessing an associated directory entry, whereinthe associated directory entry defines the protocol for communicatingwith the corresponding external data source and initiating the one ormore native requests.
 6. The method of claim 1, wherein generating theenriched database query response further comprises converting dataprovided by the at least one external data source in response to thenative requests into the enriched database query response and returninga view corresponding to the enriched database query response, orpopulating table data with the enriched database query response, orboth.
 7. The method of claim 1, wherein generating the enriched databasequery response further comprises receiving internal data from aninternal database operation, and combining the internal data with thedata provided by the at least one external data source.
 8. The method ofclaim 1, wherein processing the database query further comprisesextracting at least one parameter from the database query, wherein theat least one parameter is configured to access certain data from the atleast one external data source.
 9. The method of claim 1, whereinprocessing the database query further comprises extracting at least oneparameter from the database query, wherein the at least one parameter isconfigured to access certain data from the at least one external datasource, and wherein the at least one parameter comprises a time orlocation parameter, or both.
 10. The method of claim 1 furthercomprising, connecting to an external data source, identifying aprotocol for communicating with the external data source, and storingdata associated with utilizing the protocol to request data from theexternal data source.
 11. The method of claim 10, wherein storing thedata associated with utilizing the protocol to request data furthercomprises storing one or more credentials that are configured toauthenticate the database queries at the external data sources, orstoring one or more formats associated with data that is used by theexternal data sources, or both storing one or more credentials that areconfigured to authenticate the database queries at the external datasources and storing one or more formats associated with data that isused by the external data sources.
 12. The method of claim 10, whereinstoring the data associated with utilizing the protocol to request datafurther comprises storing the data in a directory entry, wherein thedirectory entry is utilized to produce native requests for the externaldata source based on the database queries.
 13. In a computingenvironment, a system, comprising: an enrichment service configured toidentify at least one parameter from a database query, the enrichmentservice coupled to a translation mechanism that is configured to produceone or more native requests for accessing data from at least oneexternal data source, wherein the native requests include datacorresponding to the at least one parameter, and wherein the translationmechanism is further configured to communicate the one or more nativerequests to the at least one external data source.
 14. The system ofclaim 13, wherein the enrichment service is further configured toreceive data from the one or more external data sources and to combinedata retrieved via an internal database operation with the data from theone or more external data sources.
 15. The system of claim 13, whereinthe translation mechanism identifies at least one protocol forrequesting data from the at least one external data source, connectswith the at least one external data source using the at least oneprotocol and initiates one or more requests based upon the protocol. 16.The system of claim 13 further comprising a directory configured tostore protocol-related data associated with communicating with the oneof the at least one external data sources, and wherein the enrichmentservice accesses the directory to obtain the protocol-related data foran external data source.
 17. The system of claim 13, wherein theenrichment service maps at least one entity component to the at leastone external data source based on a policy.
 18. One or morecomputer-readable media having computer-executable instructions, whichwhen executed perform steps, comprising: extracting one or moreparameters from a database query, including an entity identifier;identifying an external data source for an entity componentcorresponding to the entity, in which the entity component is known fromthe database query; communicating with the external data source toobtain data for the entity component; and returning an enriched databasequery response to the query, the enriched database query response dataincluding data corresponding to the data provided by the external datasource for the entity component.
 19. The one or more computer-readablemedia of claim 18 having further computer-executable instructionscomprising: inserting at least some of the data from the enricheddatabase query response data into an internal database table.
 20. Theone or more computer-readable media of claim 19 having furthercomputer-executable instructions comprising: automatically refreshingthe internal database table on a scheduled basis with data from anautomatically generated enriched database query.